Predicting resource usage of an application in a virtual environment

ABSTRACT

Described herein is a system for predicting resource usage of an application running in a virtual environment. The system comprises a first hardware platform implementing a native hardware system in which an application natively resides and executes, the native hardware system operating to execute a predetermined set of benchmarks that includes at least one of: a computation-intensive workload, a network-intensive workload, and a disk-intensive workload; a second hardware platform implementing a virtual environment therein, the virtual environment operating to execute the predetermined set of benchmarks; a third hardware platform operating to collect first resource usage traces from the first hardware platform and second resource usage traces from the second hardware platform; wherein the third hardware platform further operating to generate at least one prediction model that predicts a resource usage of the application executing in the virtual environment based on the collected first and second resource usage traces.

CROSS-REFERENCE

This application is related to the following applications:

a) U.S. patent application Ser. No. 12/241,913, entitled, “IMPROVING ACCURACY IN A PREDICTION OF RESOURCE USAGE OF AN APPLICATION IN A VIRTUAL ENVIRONMENT,” as filed on Sep. 30, 2008;

b) U.S. patent application Ser. No. 12/241,948, entitled, “SCALING A PREDICTION MODEL OF RESOURCE USAGE OF AN APPLICATION IN A VIRTUAL ENVIRONMENT,” as filed on Sep. 30, 2008;

c) U.S. patent application Ser. No. 12/241,988, entitled, “OPTIMIZING A PREDICTION OF RESOURCE USAGE OF AN APPLICATION IN A VIRTUAL ENVIRONMENT,” as filed on Sep. 30, 2008;

d) U.S. patent application Ser. No. 12/241,972, entitled, “DETECTING AN ERROR IN A PREDICTION OF RESOURCE USAGE OF AN APPLICATION IN A VIRTUAL ENVIRONMENT,” as filed on Sep. 30, 2008, now U.S. Pat. No. 7,818,145; and

e) U.S. patent application Ser. No. 12/242,034, entitled, “OPTIMIZING A PREDICTION OF RESOURCE USAGE OF MULTIPLE APPLICATIONS IN A VIRTUAL ENVIRONMENT,” as filed on Sep. 30, 2008.

These applications are herein incorporated by reference in their entireties.

BACKGROUND

Virtualization and automation are key capabilities desired of Next Generation Data Centers (NGDC) for enterprises. As referred herein, a data center typically includes a location, such as a room that houses computer systems and associated components to store and manage data critical to the mission(s) of an enterprise. The primary motivation for enterprises to adopt virtualization technologies is the promise of creating a more agile and dynamic information technology (IT) infrastructure. To achieve this goal, virtualization technologies have been used to implement server consolidation so as to reduce the total number of servers in response to the problem of server sprawl in a data center. Server sprawl occurs when multiple, under-utilized servers take up more space and consume more resources than can be justified by their workloads.

One example of virtualization technologies being adopted for server consolidation is the Virtual Machine Monitor (VMM), also known as a Virtual Machine (VM) host or a hypervisor. The VMM is a software component or layer that is implemented in a physical or hardware machine, system, or platform to host VM guests therein, which are isolated virtual environments on the shared hardware platform. Accordingly, VMMs enable diverse applications to run in isolated environments on a shared hardware platform, and in such a way so as to provide some degree of fault and performance isolation between the consolidated applications.

As virtual machines and systems enter the mainstream and are deployed in larger numbers for implementation of NGDCs, manageability, automation, accurate resource accounting and quality-of-service-aware (QoS-aware) resource allocation have become the real differentiators to help enterprises create dynamic IT infrastructures for their NGDCs.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments are illustrated by way of example and not limited in the following figure(s), in which like numerals indicate like elements, in which:

FIGS. 1A-B illustrate popular Input/Output (I/O) models of Xen® Virtual Machines.

FIG. 2 illustrates the goal of using native application traces to predict virtualized application traces, in accordance with one embodiment.

FIGS. 3A-B illustrate examples of the use of hardware platforms to implement native hardware system for an application and a virtual environment in which the application may be virtualized for execution, in accordance with one embodiment.

FIG. 4 illustrates a process for predicting resource usage of an application running in a virtual environment platform as it is transferred from its native hardware system, in accordance with one embodiment.

FIG. 5 illustrates a computerized system that may be used as platform to implement a native hardware system, a virtual system, and/or a client system, in accordance with one embodiment.

DETAILED DESCRIPTION

For simplicity and illustrative purposes, the principles of the embodiments are described by referring mainly to examples thereof. In the following description, numerous specific details are set forth in order to provide a thorough understanding of the embodiments. It will be apparent however, to one of ordinary skill in the art, that the embodiments may be practiced without limitation to these specific details. In other instances, well known methods and structures are not described in detail so as not to unnecessarily obscure the description of the embodiments.

A typical approach for evaluating which workloads can be efficiently consolidated together is based on multi-dimensional “bin packing” of resource usage traces. Typically, under such an approach, each application is characterized by its CPU, I/O and memory usage over time. Then a bin packing algorithm finds a combination of workloads with resource requirements which do not exceed the available server resources (some algorithms may allow a certain degree of resource overbooking as well as some additional constraints on workload placement). After the initial workload placement is done, additional workload management tools may be used to dynamically allocate system resources to match underlying application demands and to support the required application performance.

As described herein, various embodiments are concerned with the initial workload placement phase that receives as an input the application resource usage traces of its native hardware system or platform. It is important to know what an application's resource needs are going to be prior to transitioning it to a virtual environment with one or more virtual machines (VMs) therein. Resource requirements (in particular, CPU requirements) can increase due to virtualization overheads. If these overheads are not accounted for during initial planning, an application could be deployed to a server with insufficient resources, resulting in unacceptable application performance.

As illustrated in FIGS. 1A-B, there are two popular I/O models for VMs. These two VM models are demonstrated, for example, in the evolution of the I/O architecture of Xen®, which is an open-source VMM or hypervisor that serves as an abstraction layer between the physical hardware 180 and one or more VM guests 120 (hereinafter, “VM 120”). In its original design, as illustrated in FIG. 1A, the Xen hypervisor 110 itself contained device driver code, as illustrated by the network driver 112 and disk driver 114, and provided safe, shared access for I/O hardware, as illustrated by the Network Interface Card or Controller (NIC) 116 and the disk drive 118, for the VM guest 120. In its current design, as illustrated in FIG. 1B, the Xen hypervisor 110 no longer hosts device driver code. Instead, unmodified device drivers, such as the network driver 112 and disk driver 114, are allowed to be hosted and executed in one or more isolated “driver domains,” as illustrated by a management Domain-0 130 (hereinafter, “dom-0 130”). Typically, the dom-0 130 hosts unmodified device drivers, such as Linux® device drivers, and plays the role of the driver domain. Thus, the current I/O model in FIG. 1B results in a more complex CPU usage model. That is, for I/O intensive applications, CPU usage has two components: CPU consumed by the VM guest 120 and CPU consumed by the dom-0 130 which hosts the device drivers 112, 114 and performs I/O processing on behalf of the guest domain 120. Note that a trace is an ordered series, such as a time series, of monitored or collected data on performance metrics (for example, resource usage metrics of an application) of a system such as a server. Application resource usage traces are routinely collected over some time period (e.g., 3-6 months) to get a representative application resource usage profile. Then these traces can be used for capacity planning and workload placement or for other uses.

Accordingly, various embodiments as described herein provide a methodical approach for predicting the CPU requirements of applications (or workloads) when they are transferred to a virtual environment. That is, given resource utilization traces of an application running natively on its hardware system or platform, the various embodiments aim to predict what the application's resource requirements would be if it were transitioned to a virtual environment on a given hardware platform. For example, a collection of application resource usage traces (over time) in a native hardware system or platform is monitored and provided as shown in FIG. 2 at the top to show CPU utilization 210, transferred and received networking packets 212, and read and write bytes (disk) 214. The goal is to use these native application resource usage traces to predict virtualized application traces, or resource needs in a virtual environment to run the same application. Namely, as shown in FIG. 2 at the bottom, the predicted resource needs are the CPU requirement 220 of the VM guest domain 120 where the application is going to reside and execute and the CPU requirement 222 of the dom-0 130 which performs I/O processing on behalf of the VM guest domain 120 to facilitate the execution of the application within the later.

As described herein, it is expected that the CPU utilization of the VM guest 120 is highly correlated and proportional to the native CPU usage profile of the application, while the CPU utilization of the dom-0 130 is mostly determined by a combination of I/O profiles (both network and disk). As also described herein, there is a focus on predicting CPU utilization in the virtualization system because other performance metrics, such as disk and network request rates, are not directly impacted by the virtualization layer. As used herein, “disk” or “disk memory” refers to the main storage mechanism used to store data as opposed to cache memory such as Random Access Memory (RAM) chips in a hardware system. Disk memory may include, for example, a hard disk drive and/or a removable storage drive representing a floppy diskette drive, a magnetic tape drive, a compact disk drive, etc., or a nonvolatile memory where a copy of the software is stored. Disk memory may also include, for example, ROM (read only memory), EPROM (erasable, programmable ROM), EEPROM (electrically erasable, programmable ROM), or any other electronic, optical, magnetic, or other storage or transmission device capable of electronic data storage.

In one embodiment, the prediction of CPU requirements of virtualized applications (that is, applications running in a virtual environment or system) includes the following components: a) a benchmark suite having a predetermined set of benchmarks to profile the different types of virtualization overhead on a given hardware platform, whereby the benchmark suite is executed on the native hardware and in a virtual environment to create a “native” resource usage profiles and a “virtual” resource usage profiles; and b) regression-based computation to create a model that maps the “native” hardware system usage profile into the “virtual” one, whereby this model helps to predict the resource requirements of any application to be virtualized on a given hardware platform.

Accordingly, the benchmark suite is first used to accumulate samples of resource usage profiles by executing the suite's predetermined set of benchmarks in both native and virtual environments so as to determine a general relationship between the application resource usage in native and virtual systems. Then a model may be created for the virtual environment or system, which is hosted or implemented on the same or different hardware system as the native hardware system, to predict resource requirements for the virtualized application. For example, FIG. 3A illustrates the use of a native system resource usage profile 310 and a virtual system resource usage profile 320 running on separate hardware systems or platforms #1 and #2 to generate or create a first model 350 for predicting resource requirements of a virtualized application. However, the hardware systems #1 and #2 have substantially identical system configurations, such as both hardware systems #1 and #2 are AMD® Opteron™ systems. Thus, the hardware systems #1 and #2 may be one and the same. In another example, FIG. 3B illustrates the use of a native system resource usage profile 310 running on separate hardware systems (or platforms) #1 and #3 to generate or create a second different model 360 for predicting resource requirements of a virtualized application. However, the hardware systems #1 and #3 have different system configurations, such as the hardware system #1 may be an AMD® Opteron™ system and the hardware system #3 may be an Intel® Xeon™ system. The benchmark suite and prediction modeling are further detailed below.

At a high level, the benchmark suite includes three types or patterns of workload that serve as benchmarks to cause a test system (hardware or virtual) to perform CPU-intensive computation, send and receive network packets, and read and write to disk. A client system may be used to provide inputs to the test system so as to adjust the rate and type of requests to control the amount (intensity) of CPU computation and I/O activities performed on the test system. The same client system also may be used to generate the prediction model for resource usage of a virtualized application.

As referred herein, a CPU-intensive workload predominantly takes up the computational resources, such as CPU resources, of a test system during its execution in the test system while remaining minimally taxing to other resources, such as networking and memory I/O resources, of the test system. For example, the CPU-intensive computation workload calculates the Fibonacci series when it receives a request from, for example, a client system. The number of terms in such a series may be varied to adjust the load and computation time on the test system. It should be understood that other mathematical algorithms or known computational intensive algorithms may be used in lieu of the Fibonacci series for the CPU-intensive computation workload.

Similarly, as referred herein, a network-intensive workload predominantly takes up the networking resources of the test system during its execution in the test system while remaining minimally taxing to other resources of the test system. In one embodiment, the network-intensive workload has two modes depending on the type of client request. In transmit mode, each incoming client request results in a large file being sent from the system being tested to the client system. In receive mode, one or more clients upload files to the benchmark application. The size of transferred files and the rate of client requests may be varied to adjust the network utilization rate.

Likewise, as referred herein, a disk- or memory-intensive workload predominantly takes up the memory I/O resources of the test system during its execution in the test system while remaining minimally taxing to other resources of the test system. In one embodiment, the disk-intensive workload has read and write modes. In these two modes, a random file is either, respectively, read from or written to a multi-level directory structure. File size and request rate may be adjusted to control the disk I/O rate.

Accordingly, each workload is created by adjusting the request type sent to the test system from a client system or machine. In one embodiment, each type of CPU-, network-, and disk-intensive workload patterns is further divided into several (for example, five) different intensities ranging from 10% load to 90% maximum load on the test system. The maximum load that a test system can handle is determined by increasing the throughput of benchmark requests from the client until either the CPU of the VM 120 or dom-0 130 becomes saturated during testing. The range of intensities are then measured for each benchmark type in order to build an accurate prediction model for the full working range of the virtual server. In one embodiment, the benchmark suite may be implemented as a set of Hypertext Preprocessor (PHP) scripts running on a web server at the bench-marked server side. Thus, the benchmark suite may be easily deployed and executed as software applications on a wide range of hardware systems or platforms within a software environment that is already familiar with data center administrators. Consequently, the developed benchmark suite is operable to generate a diverse set of simple and more complex workloads that exercise different components of a test system.

While the benchmark suite is running or executing on each test system, namely, the native hardware system and the virtual system, resource utilization traces of each system are gathered or collected, for example, by an automated benchmark system, to define the platform profiles used as the training data for the prediction model. In one embodiment, within the native hardware system, resource utilization traces of eleven different resource metrics or measurements related to CPU utilization, network activity, and disk I/O are gathered or collected. A list of these resource metrics is shown in Table 1. Within the virtual system based on the current I/O model illustrated in FIG. 1B, resource utilization traces of two CPU utilization metrics for the VM 120 and dom-0 130 are also collected or gathered. Alternatively, if the original I/O model of VM as illustrated in FIG. 1A is employed, resource utilization traces of two CPU utilization metrics for the VM 120 and hypervisor 110 are collected or gathered. These resource utilization traces are to be gathered or collected with low overhead. Furthermore, because these traces are to be gathered from a live application being transitioned to a virtual environment, a lightweight monitoring system may be used to gather data. For example, they may be gathered in Linux™ with the Sysstat monitoring package.

TABLE 1 CPU Utilization Network Utilization Disk Utilization User Space % Rx packets/sec Read requests/sec Kernel % Tx packets/sec Write requests/sec I/O Wait % Rx bytes/sec Read blocks/sec Tx bytes/sec Write blocks/sec

The time and workload type of each resource utilization trace are stored to simplify data processing and allow for the possibility of targeted benchmark reruns. As shown in Table 1, three CPU-related metrics are monitored, namely, the user space % CPU utilization, the kernel space % CPU utilization, and the I/O wait % CPU utilization, because different types of activities may have different virtualization overheads. For example, user space processing such as simple arithmetic operations performed by an application are unlikely to have much overhead in current virtualization platforms. In contrast, tasks which occur in the kernel space, such as context switches, memory management, and I/O processing, are likely to have a higher level of overhead because they may use traps to the hypervisor. User space % CPU utilization refers to the percentage (%) of CPU resources used to run the user space (defined by an operating system that manages the native hardware system) and any application executing therein, kernel space % CPU utilization refers to the percentage of CPU resources used to run the kernel space (also defined by the operating system that manages the native hardware system), and I/O wait % CPU utilization refers to the percentage of CPU resources that are tied up while an application is waiting for I/O operations such as read and write.

For network utilization, both the packet rates and byte rates of the network interfaces are measured or monitored because different virtual environments may handle I/O virtualization in different ways. For example, prior to Xen version 3.0.3, incoming network packets were passed between the dom-0 130 and the VM guest domain 120 by flipping ownership of memory pages. Thus, the CPU overhead associated with receiving each packet was independent of the packet's size. Newer versions of Xen directly copy packets from the dom-0 130 to the VM guest domain 120 rather than using page flipping. Thus, the overhead is also related to the number of bytes received per second, not just the number of packets. The paths for sending and receiving are differentiated because they may have different optimizations. For disk (or memory) utilization, disk measurements are divided into four categories based on similar reasoning as also shown in Table 1.

Table 2 shows a sample of platform profile of collected resource usage traces of the executed benchmark suite. The first column indicates the time intervals at which the traces are collected. The second column provides an identification of the particular benchmark set in the benchmark suite, which is executed to generate the associated resource utilization traces that form the benchmark data for the particular benchmark set so that the same benchmark set may be used for a rerun as desired in the future. For example, a benchmark suite may include multiple benchmark sets, with each set created from one or more workload types and different workload parameters therein, such as different I/0 rates, load intensities, etc. The next eleven columns indicate benchmark data collected on the native hardware system for each of the eleven selected resource utilization metrics noted above. The last two columns indicate data collected for CPU utilizations of the VM guest domain 120 and the dom-0 130 in the virtual environment, as also noted above for the current I/O model of VM illustrated in FIG. 1B. Again, alternatively, if the original I/O model of VM as illustrated in FIG. 1A is employed by the native system, the last two columns are used to indicate data collected for CPU utilizations of the VM guest domain 120 and hypervisor 110 as percentages of total CPU resources available in the virtual system.

TABLE 2 . . . Benchmark User Rx . . . Rd Write CPU CPU Time Int. ID CPU % . . . Pkts/s . . . Blks/s Blks/s VM % D-0 % 1 1 22 . . . 500 . . . 80 120 24 8 2 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Using a regression-based approach, a prediction model is generated or created to map the native hardware system usage profile into a virtual one. This model helps to predict the resource requirements of any application to be virtualized on a given hardware platform. Thus, to find the relationship between the application resource usage in native and virtual systems, the collected resource usage platform profile, such as the one shown in Table 2, is used to form a set of equations that calculate CPU utilization of the dom-0 130 as a linear combination of the different metrics: U _(dom0) ¹ =c ₀ +c ₁ *M ₁ ¹ +c ₂ *M ₂ ¹ + . . . +c ₁₁ *M ₁₁ ¹ U _(dom0) ² =c ₀ +c ₁ *M ₁ ² +c ₂ *M ₂ ² + . . . +c ₁₁ *M ₁₁ ²  (1) where M_(j) ^(i) is a value of metric M_(i) collected during the time interval j for a benchmark set executed in the native environment, and U_(dom0) ^(j) is a measured CPU utilization for a benchmark set executed in the virtual environment (for example, domain-0 130) with the corresponding time interval j.

With c₀ ^(dom0), c₁ ^(dom0), . . . , c₁₁ ^(dom0) denoting the approximated solution for the equation set (1), an approximated utilization Û_(dom0) ^(j) is calculated as:

$\begin{matrix} {{\overset{\Cap}{U}}_{{dom}\; 0}^{j} = {c_{0}^{{dom}\; 0} + {\sum\limits_{i = 1}^{11}\;{M_{i}^{j} \cdot c_{i}^{{dom}\; 0}}}}} & (2) \end{matrix}$ To solve for c_(i) ^(dom0) (0≦i≦11), any regression method may be used. For example, the least squares regression method may be used to solve the set of equations (1) and (2) so as to calculate the coefficients c₀ ^(dom0), c₁ ^(dom0), . . . , c₁₁ ^(dom0) while minimizing the error:

$\begin{matrix} {e = \sqrt{\sum\limits_{j}\;\left( {{\overset{\Cap}{U}}_{{dom}\; 0}^{j} - U_{{dom}\; 0}^{j}} \right)_{j}^{2}}} & (3) \end{matrix}$

The set of coefficients c₀ ^(dom0), c₁ ^(dom0), . . . , c₁₁ ^(dom0) is a first prediction model that describes the relationship between the application resource usage in the native system and application CPU usage in the dom-0 130. Another set of equations similar to the set of equations (1) are also formed to characterize the CPU utilization of the VM guest domain 120 by replacing U_(dom0) ^(i) with U_(vm) ^(i). The resulting solution c₀ ^(vm), c₁ ^(vm), . . . , c_(n) ^(vm) then defines a second prediction model that relates the application resource usage in the native system and application CPU usage in the VM 120 running the application. Thus, with known values of M_(j) ^(i) for metrics M_(i) at time intervals j for an application running in the native system and known sets of coefficients c₀ ^(dom0), c₁ ^(dom0), . . . , c₁₁ ^(dom0) and c₀ ^(vm), c₁ ^(vm), . . . , c_(n) ^(vm), the sets of equations (2) for both U_(dom0) ^(i) and U_(vm) ^(i) may be used to effectively predict the resource usage of the same application when virtualized in a particular virtual system.

Accordingly, FIG. 4 illustrates a method 400 for predicting resource usage, particularly, CPU requirements, of an application running in a virtual environment or system as it is transferred from its native hardware system, in accordance with one embodiment. For illustrative purposes only and not to be limiting thereof, FIG. 4 is discussed with reference to the VM model illustrated in FIG. 1B and systems illustrated in FIGS. 3A-B.

At 410, a benchmark suite is prepared or provided to include a plurality of benchmark sets of benchmarks of CPU-intensive computation, network-intensive, and disk-intensive workloads as described earlier.

At 412, the benchmark suite is executed in a native hardware system so as to gather resource utilization traces of such a system as it executes the benchmark suite. The native hardware system is, for example, the hardware system #1 in FIGS. 3A-B that is initially used to natively run a desired application which is now desired to be run in a desired virtual environment or system within the same hardware system #1 (FIG. 3A) or in a different hardware system #2 (FIG. 3B).

At 414, the resource utilization traces of the native hardware system (that is, the traces of the eleven resource utilization metrics in the native hardware system) are collected to form a native hardware system profile while the benchmark suite is running therein.

At 416, the benchmark suite is also executed in the desired or selected virtual environment that is to replace the native hardware system for running the desired application.

At 418, the resource utilization traces of the virtual system (that is, the traces of the two CPU utilization metrics in the virtual system) are also collected to form a virtual system profile while the benchmark suite is running in the virtual system.

At 420, as described earlier, one or more prediction models are generated using a regression-based approach to map the native hardware system profile to the virtual system profile.

At 422, the prediction model may be used to predict a resource usage of an application running in the virtual system once it migrates over from the hardware system in which it natively resides and runs. That is, once a prediction model is generated or created, it may be applied to resource utilization traces of other applications in order to predict what their CPU requirements are going to be once they are transferred to a virtual environment.

The method 400 as illustrated in FIG. 4 is also applicable for generating prediction models for the hypervisor 110 and VM 1200 for a virtual environment that follows the VM model illustrated in FIG. 1A.

FIG. 5 illustrates a block diagram of a computerized system 500 that is operable to be used as a platform for implementing a client system that may be used to provide inputs to the test native hardware and virtual systems to generate the prediction model as described earlier. Another computerized system 500 may also serve as a native hardware system and/or a hardware platform on which a virtual system is implemented.

The computer system 500 includes one or more processors, such as processor 502, providing an execution platform for executing software. Thus, the computerized system 500 includes one or more single-core or multi-core processors of any of a number of computer processors, such as processors from Intel, AMD, and Cyrix. As referred herein, a computer processor may be a general-purpose processor, such as a central processing unit (CPU) or any other multi-purpose processor or microprocessor. A computer processor also may be a special-purpose processor, such as a graphics processing unit (GPU), an audio processor, a digital signal processor, or another processor dedicated for one or more processing purposes. Commands and data from the processor 502 are communicated over a communication bus 504 or through point-to-point links with other components in the computer system 500.

The computer system 500 also includes a main memory 506 where software is resident during runtime, and a secondary memory 508. The secondary memory 508 may also be a computer-readable medium (CRM) that may be used to store software programs, applications, or modules that implement the method or process 400 in FIG. 4, applications running natively, and/or components for a virtual environment (such as a hypervisor, driver domains, and VM guests). The main memory 506 and secondary memory 508 (and an optional removable storage unit 514) each includes, for example, a hard disk drive 510 and/or a removable storage drive 512 representing a floppy diskette drive, a magnetic tape drive, a compact disk drive, etc., or a nonvolatile memory where a copy of the software is stored. In one example, the secondary memory 508 also includes ROM (read only memory), EPROM (erasable, programmable ROM), EEPROM (electrically erasable, programmable ROM), or any other electronic, optical, magnetic, or other storage or transmission device capable of providing a processor or processing unit with computer-readable instructions. The computer system 500 includes a display 520 connected via a display adapter 522, user interfaces comprising one or more input devices 518, such as a keyboard, a mouse, a stylus, and the like. However, the input devices 518 and the display 520 are optional. A network interface 530 is provided for communicating with other computer systems via a network, such as the Internet or an intranet. For example, if the computerized system 500 is used to implement the client system, the network interface 530 may be used to provide inputs to the test systems via a network and receive resource usage traces from the test systems. If the computerized system 500 is used as a hardware platform for the native hardware or virtual systems, the network interface 530 may be used to communicate with the client system to receive inputs for running the benchmark suite and provide resulting resource usage traces to the client system.

What has been described and illustrated herein is an embodiment along with some of its variations. The terms, descriptions and figures used herein are set forth by way of illustration only and are not meant as limitations. Those skilled in the art will recognize that many variations are possible within the spirit and scope of the subject matter, which is intended to be defined by the following claims—and their equivalents—in which all terms are meant in their broadest reasonable sense unless otherwise indicated. 

1. A method for predicting resource usage of an application running in a virtual environment, comprising: providing a predetermined set of benchmarks, wherein the predetermined set of benchmarks includes at least one of: a computation-intensive workload; a network-intensive workload; and a disk-intensive workload; executing the predetermined set of benchmarks in a native hardware system in which the application natively resides; executing the predetermined set of benchmarks in the virtual environment; collecting first traces of resource utilization metrics in the native hardware system based on the execution of the predetermined set of benchmarks in the native hardware system; collecting second traces of resource utilization metrics in the virtual environment based on the execution of the predetermined set of benchmarks in the virtual environment; generating at least one prediction model that maps the first traces of resource utilization metrics to the second traces of resource utilization metrics; and predicting a resource usage of the application running in the virtual environment with the at least one prediction model.
 2. The method of claim 1, wherein providing the predetermined set of benchmarks comprises: providing at least one of the computation intensive, network intensive, and disk intensive workloads at a plurality of load intensities on the native hardware system and the virtual environment.
 3. The method of claim 1, further comprising: hosting the virtual environment on a hardware platform that has substantially the same hardware configurations as the native hardware system.
 4. The method of claim 1, wherein collecting the first traces of resource utilization metrics in the native hardware system comprises at least one of: first collecting a percentage of processor utilization in the native hardware system that is attributed to a utilization of hardware processing resources in the native hardware system by a user space therein during an execution of the predetermined set of benchmarks; second collecting a percentage of processor utilization in the native hardware system that is attributed to a utilization of processing resources in the native hardware system by a kernel therein; and third collecting a percentage of processor utilization in the native hardware system that is attributed to a utilization of processing resources in the native hardware system by an input/output (I/O) wait therein.
 5. The method of claim 1, wherein collecting the first traces of resource utilization metrics in the native hardware system comprises at least one of: first collecting a network packet rate of data packets received from a data network by the native hardware system; second collecting a network packet rate of data packets transmitted through the data network by the native hardware system; third collecting a network byte rate of data bytes received from the data network by the native hardware system; and fourth collecting a network byte rate of data bytes transmitted through the data network by the native hardware system.
 6. The method of claim 1, wherein collecting the first traces of resource utilization metrics in the native hardware system comprises at least one of: first collecting a rate of disk read requests that is received by the native hardware system for accessing a disk memory therein; second collecting a rate of disk write requests that is received by the native hardware system for accessing a disk memory therein; third collecting a rate of memory blocks requested for reading that is received by the native hardware system for accessing a disk memory therein; and fourth collecting a rate of memory blocks requested for writing that is received by the native hardware system for accessing a disk memory therein.
 7. The method of claim 1, wherein collecting second traces of resource utilization metrics in the virtual environment comprises: first collecting a percentage of processor utilization in the virtual environment that is attributed to a utilization of hardware processing resources by a driver domain within the virtual environment; and second collecting a percentage of processor utilization in the virtual environment that is attributed to a utilization of hardware processing resources by a virtual machine (VM) guest within the virtual environment.
 8. The method of claim 1, wherein generating the prediction model comprises: performing a first calculation to generate a first prediction model for estimating a resource usage of the driver domain when the application is running in the virtual environment; and performing a second calculation to generate a second prediction model for estimating a resource usage of the VM guest when the application is running in the virtual environment.
 9. A system for predicting resource usage of an application running in a virtual environment, comprising: a first hardware platform implementing a native hardware system in which an application natively resides and executes, the native hardware system operating to execute a predetermined set of benchmarks that includes at least one of: a computation-intensive workload; a network-intensive workload; and a disk-intensive workload; a second hardware platform implementing a virtual environment therein, the virtual environment operating to execute the predetermined set of benchmarks; a third hardware platform operating to collect first resource usage traces from the first hardware platform that result from the execution of the predetermined set of benchmarks in the native hardware system and second resource usage traces from the second hardware platform that result from the execution of the predetermined set of benchmarks in the virtual environment; wherein the third hardware platform further operating to generate at least one prediction model that predicts a resource usage of the application executing in the virtual environment based on the collected first and second resource usage traces.
 10. The system of claim 9, wherein the third hardware platform further operating to provide the predetermined set of benchmarks for execution by the native hardware system and the virtual environment.
 11. The system of claim 10, wherein the third hardware platform further operating to vary a load intensity of at least one benchmark in the predetermined set of benchmarks for execution by the native hardware system and the virtual environment.
 12. The system of claim 10, wherein the third hardware platform further operating to provide a plurality of load intensities for each benchmark in the predetermined set of benchmarks for execution by the native hardware system and the virtual environment.
 13. The system of claim 9, wherein the first resource usage traces comprises: at least one of a percentage of processor utilization in the native hardware system that is attributed to a utilization of hardware processing resources in the first hardware platform by a user space in the native hardware system, a percentage of processor utilization in the native hardware system that is attributed to a utilization of processing resources in the first hardware platform by a kernel in the native hardware system, and a percentage of processor utilization in the native hardware system that is attributed to a utilization of processing resources in the first hardware platform by an input/output (I/O) wait therein; at least one of a network packet rate of data packets received from a data network by the first hardware platform, a network packet rate of data packets transmitted through the data network by the first hardware platform, a network byte rate of data bytes received from the data network by the first hardware platform, and a network byte rate of data bytes transmitted through the data network by the first hardware platform; and at least one of a rate of disk read requests that is received by the first hardware platform for accessing a disk memory therein, a rate of disk write requests that is received by the first hardware platform for accessing a disk memory therein, a rate of memory blocks requested for reading that is received by the first hardware platform for accessing a disk memory therein, and a rate of memory blocks requested for writing that is received by the first hardware platform for accessing a disk memory therein.
 14. The system of claim 9, wherein the virtual environment includes a driver domain and a virtual machine (VM) guest domain, and the second resource usage traces comprises: a percentage of processor utilization in the virtual environment that is attributed to a utilization of hardware processing resources in the second hardware platform by the driver domain; and a percentage of processor utilization in the virtual environment that is attributed to a utilization of hardware processing resources in the second hardware platform by the VM guest domain.
 15. A non-transitory computer readable medium storing computer executable programming code which when executed by a computer processor predicts resource usage of an application running in a virtual environment, the programming code comprising: programming code for providing a predetermined set of benchmarks, wherein the predetermined set of benchmarks includes at least one of: a computation-intensive workload; a network-intensive workload; and a disk-intensive workload; programming code for executing the predetermined set of benchmarks in a native hardware system in which the application natively resides; programming code for executing the predetermined set of benchmarks in the virtual environment; programming code for collecting first traces of resource utilization metrics in the native hardware system based on the execution of the predetermined set of benchmarks in the native hardware system; programming code for collecting second traces of resource utilization metrics in the virtual environment based on the execution of the predetermined set of benchmarks in the virtual environment; programming code for generating a prediction model that maps the first traces of resource utilization metrics to the second traces of resource utilization metrics; and programming code for predicting a resource usage of the application running in the virtual environment with the prediction model. 